From an external API, we can start DOORS with a batch script, which can start the dxl server in a pseudo mode and connect to it. If not initialized while trying to connect to the TCPIP socket/server, and waiting for connections, then our call to attach to it fails and ends the application without returning an error.
Here's the expectation:
If the DOORS is not listening through the ConnectSocket API, then we should get a returned exception...then we can either choose to wait or start something up.
Questions:
(1) Why is no error code received if the ConnectSocket API is exited/if we can not connect?
(2) Can we write the client socket connection ourselves? -- Is there anything specific to the DOORS API implementation that would prevent such a thing?
Note: I'm posting this question for someone else. With my limited DOORS API experience I don't fully understand the question, but hopefully it makes since the readers of this board.
SystemAdmin - Wed May 13 16:52:04 EDT 2009 |